home *** CD-ROM | disk | FTP | other *** search
ggggeeeennnnccccaaaatttt((((1111)))) ggggeeeennnnccccaaaatttt((((1111)))) NNNNAAAAMMMMEEEE _gggg_eeee_nnnn_cccc_aaaa_tttt - generate a formatted message catalogue SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS _gggg_eeee_nnnn_cccc_aaaa_tttt [_----_mmmm] _c_a_t_f_i_l_e _m_s_g_f_i_l_e ... DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN The _gggg_eeee_nnnn_cccc_aaaa_tttt utility merges the message text source file(s) _m_s_g_f_i_l_e into a formatted message database _c_a_t_f_i_l_e. The database _c_a_t_f_i_l_e will be created if it does not already exist. If _c_a_t_f_i_l_e does exist its messages will be included in the new _c_a_t_f_i_l_e. If set and message numbers collide, the new message text defined in _m_s_g_f_i_l_e will replace the old message text currently contained in _c_a_t_f_i_l_e. The message text source file (or set of files) input to _gggg_eeee_nnnn_cccc_aaaa_tttt can contain either set and message numbers or simply message numbers, in which case the set _NNNN_LLLL______SSSS_EEEE_TTTT_DDDD [see _nnnn_llll______tttt_yyyy_pppp_eeee_ssss(5)] is assumed. The meanings of the options are: _----_mmmm Use memory allocated by the _m_a_l_l_o_c() routine, instead of memory mapped allocation routine _m_m_a_p(). _----_tttt _t_e_x_t_m_a_x This is optional. This parameter _t_e_x_t_m_a_x allows _gggg_eeee_nnnn_cccc_aaaa_tttt to dynamically allocate the message text area. If not specified, then the _NNNN_LLLL______TTTT_EEEE_XXXX_TTTT_MMMM_AAAA_XXXX define is used for the message text length. If the _----_tttt option parameter is present, then the _t_e_x_t_m_a_x input must be a decimal number in the range of (0-32767). If _t_e_x_t_m_a_x is specified and is not in the range (0-32767) or is not greater than _NNNN_LLLL______TTTT_EEEE_XXXX_TTTT_MMMM_AAAA_XXXX, then the message text length maximum is set to _NNNN_LLLL______TTTT_EEEE_XXXX_TTTT_MMMM_AAAA_XXXX. The format of a message text source file is defined as follows. Note that the fields of a message text source line are separated by a single ASCII space or tab character. Any other ASCII spaces or tabs are considered as being part of the subsequent field. _$$$$_ssss_eeee_tttt _n _c_o_m_m_e_n_t Where _n specifies the set identifier of the following messages until the next _$$$$_ssss_eeee_tttt, _$$$$_dddd_eeee_llll_ssss_eeee_tttt or end-of-file appears. _n must be a number in the range (1-{_NNNN_LLLL______SSSS_EEEE_TTTT_MMMM_AAAA_XXXX}). Set identifiers within a single source file need not be contiguous. Any string following the set identifier is treated as a comment. If no _$$$$_ssss_eeee_tttt directive is specified in a message text source file, all messages will be located in the default message set _NNNN_LLLL______SSSS_EEEE_TTTT_DDDD. _$$$$_dddd_eeee_llll_ssss_eeee_tttt _n _c_o_m_m_e_n_t Deletes message set _n from an existing message catalogue. Any string following the set number is treated as a comment. (Note: if _n is not a valid set, it is ignored.) PPPPaaaaggggeeee 1111 ggggeeeennnnccccaaaatttt((((1111)))) ggggeeeennnnccccaaaatttt((((1111)))) _$$$$ _c_o_m_m_e_n_t A line beginning with a dollar symbol (_$$$$) followed by an ASCII space or tab character is treated as a comment. _m _m_e_s_s_a_g_e _t_e_x_t The _m denotes the message identifier, which is a number in the range (1-{_NNNN_LLLL______MMMM_SSSS_GGGG_MMMM_AAAA_XXXX}). The message text is stored in the message catalogue with the set identifier specified by the last _$$$$_ssss_eeee_tttt directive, and with message identifier _m. If the message text is empty, and an ASCII space or tab field separator is present, an empty string is stored in the message catalogue. If a message source line has a message number, but neither a field separator nor message text, the existing message with that number (if any) is deleted from the catalogue. Message identifiers need not be contiguous. The length of message text must be in the range (0-{_NNNN_LLLL______TTTT_EEEE_XXXX_TTTT_MMMM_AAAA_XXXX}). _$$$$_qqqq_uuuu_oooo_tttt_eeee _c This line specifies an optional quote character _c, which can be used to surround message text so that trailing spaces or null (empty) messages are visible in a message source line. By default, or if an empty _$$$$_qqqq_uuuu_oooo_tttt_eeee directive is supplied, no quoting of message text will be recognized. Empty lines in a message text source file are ignored. Text strings can contain the special characters and escape sequences defined in the following table: ___________________________________________ Description Symbol Sequence ___________________________________________ newline NL(LF) \n horizontal tab HT \t vertical tab VT \v backspace BS \b carriage return CR \r form feed FF \f backslash \ \\ bit pattern ddd \ddd ___________________________________________ ||||||||||| ||||||||||| If the character following a backslash is not one of those specified, the backslash is ignored. The escape sequence _\\\\_dddd_dddd_dddd consists of backslash followed by 1, 2, or 3 octal digits, which are taken to specify the value of the desired character. Backslash followed by an ASCII newline character is also used to continue a string on the following line. Thus, the following two lines describe a single message string: PPPPaaaaggggeeee 2222 ggggeeeennnnccccaaaatttt((((1111)))) ggggeeeennnnccccaaaatttt((((1111)))) _1111 _TTTT_hhhh_iiii_ssss _llll_iiii_nnnn_eeee _cccc_oooo_nnnn_tttt_iiii_nnnn_uuuu_eeee_ssss _\\\\ _tttt_oooo _tttt_hhhh_eeee _nnnn_eeee_xxxx_tttt _llll_iiii_nnnn_eeee which is equivalent to: _1111 _TTTT_hhhh_iiii_ssss _llll_iiii_nnnn_eeee _cccc_oooo_nnnn_tttt_iiii_nnnn_uuuu_eeee_ssss _tttt_oooo _tttt_hhhh_eeee _nnnn_eeee_xxxx_tttt _llll_iiii_nnnn_eeee FFFFIIIILLLLEEEESSSS _////_uuuu_ssss_rrrr_////_llll_iiii_bbbb_////_llll_oooo_cccc_aaaa_llll_eeee_////_l_o_c_a_l_e_////_LLLL_CCCC______MMMM_EEEE_SSSS_SSSS_AAAA_GGGG_EEEE_SSSS_////_uuuu_xxxx_mmmm_eeee_ssss_gggg language-specific message file [See _LLLL_AAAA_NNNN_GGGG on _eeee_nnnn_vvvv_iiii_rrrr_oooo_nnnn(5).] SSSSEEEEEEEE AAAALLLLSSSSOOOO _mmmm_kkkk_mmmm_ssss_gggg_ssss(1), _cccc_aaaa_tttt_oooo_pppp_eeee_nnnn(3C), _cccc_aaaa_tttt_gggg_eeee_tttt_ssss(3C), _cccc_aaaa_tttt_cccc_llll_oooo_ssss_eeee(3C), _gggg_eeee_tttt_tttt_xxxx_tttt(3C), _nnnn_llll______tttt_yyyy_pppp_eeee_ssss(5) NNNNOOOOTTTTEEEESSSS This version of _gggg_eeee_nnnn_cccc_aaaa_tttt is built on the _mmmm_kkkk_mmmm_ssss_gggg_ssss utility. The _gggg_eeee_nnnn_cccc_aaaa_tttt database consists of two files, _c_a_t_f_i_l_e_...._mmmm, which is a _mmmm_kkkk_mmmm_ssss_gggg_ssss format catalogue, and _c_a_t_f_i_l_e, which contains the information required to translate a set and message number into a simple message number that can be used in a call to _gggg_eeee_tttt_tttt_xxxx_tttt. Using _gggg_eeee_tttt_tttt_xxxx_tttt constrains the catalogues to be located in a subdirectory under _////_uuuu_ssss_rrrr_////_llll_iiii_bbbb_////_llll_oooo_cccc_aaaa_llll_eeee. This restriction is lifted by placing only a symbolic link to the catalogue in the directory _////_uuuu_ssss_rrrr_////_llll_iiii_bbbb_////_llll_oooo_cccc_aaaa_llll_eeee_////_XXXX_oooo_pppp_eeee_nnnn_////_LLLL_CCCC______MMMM_EEEE_SSSS_SSSS_AAAA_GGGG_EEEE_SSSS when the catalogue is opened. It is this link that _gggg_eeee_tttt_tttt_xxxx_tttt uses when attempting to access the catalogue. The link is removed when the catalogue is closed but occasionally as applications exit abnormally without closing catalogues redundant symbolic links will be left in the directory. For compatibility with previous versions of _gggg_eeee_nnnn_cccc_aaaa_tttt released in a number of specialized internationalization products, the _----_mmmm option is supplied. This option will cause _gggg_eeee_nnnn_cccc_aaaa_tttt to build a single file _c_a_t_f_i_l_e which is compatible with the format catalogues produced by the earlier versions. The retrieval routines detect the type of catalogue they are using and will act appropriately. PPPPaaaaggggeeee 3333 
